Received: by mail3.netcom.com (8.6.8.1/Netcom) id QAA12480; Fri, 5 Aug 1994 16:02:39 -0700
Received: from goalkeeper.d2.com by mail3.netcom.com (8.6.9/Netcom) id QAA12450; Fri, 5 Aug 1994 16:02:30 -0700
Received: from d2.com by goalkeeper.d2.com via UUCP (931110.SGI/(930416.SGI)1.0-D2.COM-OUTERELAY) for lightwave-l@netcom.com id AA16724; Fri, 5 Aug 94 16:01:09 -0700
Received: from arcadia.d2.com by omaha.d2.com via SMTP (920330.SGI/(921111.SGI)1.1-D2.COM-RELAY) for lightwave-l@netcom.com id AA04290; Fri, 5 Aug 94 16:00:32 -0700
Received: by arcadia.d2.com (920330.SGI/(921111.SGI)1.1-D2.COM) for @omaha.d2.com:lightwave-l@netcom.com id AA08106; Fri, 5 Aug 94 16:00:31 -0700
From: pockets@d2.com (Sean Cunningham)
Message-Id: <9408052300.AA08106@arcadia.d2.com>
Subject: Re: Roto
To: lightwave-l@netcom.com
Date: Fri, 5 Aug 1994 16:00:31 -0700 (PDT)
In-Reply-To: <9408051801.AA07917@ella.colossal.com> from "Mark Swain" at Aug 5, 94 11:01:58 am
X-Mailer: ELM [version 2.4 PL23beta2]
Content-Type: text
Content-Length: 1820
Sender: owner-lightwave-l@netcom.com
Precedence: list
Reply-To: lightwave-l@netcom.com
(...lots-o-stuff deleted regarding flare job...)
:) Roto in lightwave is not one of the best features in the current version
:) of the package. The method works ok for roto motion that does not need
:) to match other sources. If you are looking to match live action scenes I
:) think it is a big leap - at least until the PC & SGI version are ready!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
How so? The Windows and SGI version are going to feature the same interface
as the Amiga version of Lightwave (from the Siggraph eyewitness accounts that
I read recently). The current viewport methodology is the problem, not the
Amiga. A viewport with programmable resolution and aspect ratio will solve
this problem...there is no magic in an Intel processor or MIPS chip that
tends to make rotoscoping work or not work.
In fact, even with the current scenario accurate rotoscoping can be achieved,
it will just take more work than it really should (as if rotoscoping were not
already a pain in the rear). I intend to work out the methodology completely
if I have a chance this weekend, but the gist of it should be to "pad" your
BG plates so that they load into the viewport unsqueezed in any way. You then
make use of the LIMITED REGION rendering option, bumping up your output
resolution settings within the interface until the resolution of your LIMITED
REGION crop window matches your desired final output. It's not very elegant,
but its better than adding the extra effort and expense of fixing your roto
in post (if it can be fixed), especially on something as expensive as the